home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Inside Mac Games Volume 4 #7
/
IMG 38 July 1996.iso
/
Demos
/
Locus
/
Resource
/
INSTMENU.SCR
< prev
next >
Wrap
Text File
|
1995-12-03
|
2KB
|
51 lines
; This file uses Mike D.'s scripting routines to create a menu
; hierarchy.
; FORMAT:
; MENU (menu#1_Title, <NONE/parentMenuName>,
; entry#1_title, <SUBMENU/FUNCTION/FLYMENU>, menu/function_Name, n, "", "", ...
; entry#2_title, <SUBMENU/FUNCTION/FLYMENU>, menu/function_Name, n, "", "", ...
; .
; .
; .
; entry#n_title, <SUBMENU/FUNCTION/FLYMENU>, menu/function_Name, n, "", "", ...
; MENU_END)
;
; MENU (menu#2_Title, etc.)
;
; ...and so on.
; IMPORTANT NOTES:
; --When building the hierarchy, setup uses non-case-sensetive
; strings to identify parents and children. So you MUST NOT
; have two entries or menus with the same title!!
;
; --The root level menu will have 'None' for its parent. All other
; windows list their parent menu here. At the moment, this field
; isn't used for anything. In the future, it could provide
; a means to identify non-unique menu entries.
;
; --All entries in a menu either call a child menu or a function.
; The <SUBMENU/FUNCTION/FLYMENU> field determines the behavior
; for the corresponding entry. If you enter SUBMENU, the name
; in the first field determines which submenu the entry will
; call. You need no third field in this case (and should not
; enter one). If you enter FLYMENU, the third field defines
; a function which generates a menu on the fly and tries to
; attach it to the entry node. Writing FUNCTION to this field
; causes the entry to call the function linked to the name
; in the third field (the linkage takes place in a list in the
; list in the menuFns.c file).
;
; A simple example follows.
MENU (Main Menu, None,
Install Locus, FUNCTION, doHalfInstall, 6, This uses about 3, megabytes of space,
on your hard drive., You must have the,
CD in its drive to, play.,
Exit Install, FUNCTION, quit, 1, Aborts the install.,
MENU_END)
ENDSCRIPT